Resource state monitoring method, device and communication network

ABSTRACT

A resource state monitoring method, device and communication network are provided. The method includes: acquiring network event state information of a node in a network running process, detecting a data plane resource state of the node and a control plane resource state of the node when it determines that the network event state information of the node meets a resource state detection triggering condition, and reporting a detection result to a management plane of the node. The device includes an acquiring unit, a checking unit, a triggering unit, a detecting unit and a reporting unit. The network includes several nodes, a communication control device and a resource state monitoring device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Patent ApplicationNo. PCT/CN2008/070885, filed May 6, 2008, which claims priority toChinese Patent Application No. 200710104352.1, filed May 9, 2007, bothof which are hereby incorporated by reference in their entirety.

FIELD OF THE INVENTION

The present invention relates to the communication field, andparticularly to a resource state monitoring method, device andcommunication network.

BACKGROUND

A conventional optical network mainly adopts a self-healing ringnetworking mode and has low bandwidth utilization. Furthermore, theconventional optical network is configured statically by a networkadministrator, and mainly adopts a ring networking, which has acomplicated configuration and low bandwidth utilization, and is timeconsuming. With a requirement for multi-service, high bandwidth, highsurvivability and rapid connection provision, a network topology wouldevolve to be mainly a mesh network from being mainly a conventional ringnetwork in the existing systems, and a network connection provisionmanner should transit to a signaling-based soft permanent connection andswitched connection from a statically assigned permanent connection. Anovel optical transfer network is referred to be an AutomaticallySwitched Optical Network (ASON) or Generalized Multi-Protocol LabelSwitching (GMPLS) network.

As for network resources, the ASON/GMPLS must experience the followingthree processes before providing an available resource and forming aconsistent global topology:

1. A vertical synchronization (or local initialization): a localresource of a control plane is initialized, in other words, the controlplane acquires a view of the local resource on the control plane, forexample, connection points (CPs) of a data plane are mapped tosubnetwork points (SNPs) of the control plane, and obtain a resourcepool of a local subnetwork point pool (SNPP).

2. A horizontal synchronization (or link discovery): adjacent SNPPlinks, or referred to as traffic engineering (TE) links, are acquiredand formed through a discovery mechanism.

3. A global synchronization: each node obtains a global consistenttopology through a route flooding, e.g., an open shortest path firstprotocol-transport engineering (OSPF-TE).

In the existing systems, the ASON/GMPLS would carry out the above threesynchronization processes before providing the available resource andforming the consistent global topology, but in a network runningprocess, some inconsistency may occur between the control plane resourcestate and the data plane resource state due to a network abnormality orother operations. Moreover, there is no mechanism for detecting thecontrol plane resource state and the data plane resource state in thenetwork running process in the existing systems. Therefore, once aninconsistency occurs, the network would fail, thereby influencing thenetwork stability.

SUMMARY

The present invention is directed to a resource state monitoring method,device and communication network, so as to increase network stability.

Accordingly, an embodiment of the present invention provides a resourcestate monitoring method. In a network running process, the methodincludes: network event state information of a node is acquired, a dataplane resource state of the node and a control plane resource state ofthe node are detected when the network event state information of thenode meets a resource state detection triggering condition, and adetection result is reported to a management plane of the node.

An embodiment of the present invention further provides a resource statemonitoring device, which includes: an acquiring unit, adapted to acquirenetwork event state information of a node, a checking unit, adapted tojudge whether the network event state information of the node meets aresource state detection triggering condition or not and send atriggering notification if the network event state information of thenode meets a resource state detection triggering condition, a triggeringunit, adapted to trigger detection after receiving the triggeringnotification of the checking unit, a detecting unit, adapted to detect adata plane resource state of the node and a control plane resource stateof the node after receiving the triggering detection of the triggeringunit, and a reporting unit, adapted to report a detection result of thedetecting unit to a management plane of the node.

An embodiment of the present invention further provides a communicationnetwork, which includes several nodes, each of the nodes is adapted tocommunicate in a communication network, a communication control deviceadapted to control each of the nodes to communicate, and a resourcestate monitoring device adapted to acquire network event stateinformation of each of the nodes, detect a data plane resource state ofeach of the nodes and a control plane resource state of each of thenodes when the network event state information of the nodes meets aresource state detection triggering condition, and report a detectionresult to a management plane of each of the nodes.

It can be seen from the above technical solution that, the embodimentsof the present invention have the following beneficial effects.

In the embodiments of the present invention, during the network runningprocess, the network event state information of the node is acquired,whether the network event state information of the node meets theresource state detection triggering condition or not is determined, anda consistency of the control plane resource state of the node and thedata plane resource state of the node is detected if the network eventstate information of the node meets the resource state detectiontriggering condition. Therefore, inconsistency of the control planeresource state of the node and the data plane resource state of the nodemay be found out in time in the network running process, therebyincreasing the network running stability.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an overall flowchart of a resource state monitoring methodaccording to an embodiment of the present invention;

FIG. 2 is a flowchart of a resource state monitoring method according toa first embodiment of the present invention;

FIG. 3 is a flowchart of a resource state monitoring method according toa second embodiment of the present invention;

FIG. 4 is a flowchart of a resource state monitoring method according toa third embodiment of the present invention;

FIG. 5 is a schematic view of a resource state monitoring deviceaccording to an embodiment of the present invention; and

FIG. 6 is a schematic view of a communication network according to anembodiment of the present invention.

DETAILED DESCRIPTION

The embodiments of the present invention provide a resource statemonitoring method, device and a communication network so as to increasethe network stability.

Following embodiments are described by taking an ASON network as anexample. It may be understood that, the present invention may also bedescribed based on other similar networks, such as a GMPLS network, anda processing flow thereof is similar.

Referring to FIG. 1, an overall flow of a resource state monitoringmethod according to an embodiment of the present invention includes thefollowing steps:

Step 101: A network event state of a node is acquired.

Step 102: Whether the network event state of the node meets a resourcestate detection triggering condition or not is judged. Step 103 iscarried out if the network event state of the node meets the resourcestate detection triggering condition; and step 107 is carried out if thenetwork event state of the node does not meet the resource statedetection triggering condition.

The situations included in a specific network event state will bedescribed in the later embodiments.

The resource state detection triggering condition has three situations,which will be described in detail in later embodiments.

Step 103: A data plane resource state of the node and a control planeresource state of the node are detected.

Step 104: Whether the data plane resource state of the node and thecontrol plane resource state of the node are consistent or not isjudged. Step 106 is carried out if the data plane resource state of thenode and the control plane resource state of the node are consistent;and step 105 is carried out if the data plane resource state of the nodeand the control plane resource state of the node are not consistent.

Step 105: The data plane resource state of the node and the controlplane resource state of the node are synchronized.

Step 106: A detection result of the data plane resource state of thenode and the control plane resource state of the node is reported to amanagement plane of the node.

Step 107: The network event state of the node continues to be monitored.

In the above embodiment, during the ASON network running process, thenetwork event state of the node is acquired, whether the state meets theresource state detection triggering condition is judged, and consistencydetection is performed on the data plane resource state of the node andthe control plane resource state of the node if it is determined thatthe state meets the resource state detection triggering condition. Thus,an instability factor existing in the ASON network running process maybe found out in time, thereby increasing the network stability.

The resource states of the node in the embodiments of the presentinvention will first be illustrated in detail below.

The resource states of the node are mainly divided into a control planeresource state and a data plane resource state, and the control planeSNP state may be divided into available, potentially available, assignedand busy. The “available” state refers to that the resourcecorresponding to the SNP is in an idle state and can be used. The“potentially available” state and “busy” state are generally the statesoccur in a multi-adaptable or virtual private network (VPN), in which aconnection point (CP) of one transfer plane resource may be assigned tomultiple subnetwork points of multiple control planes to use. The“potentially available” state refers to that the resource correspondingto the transfer plane has not been assigned to any control plane ormanagement plane to use, and these control planes potentially have achance for using it. The “busy” state refers to that the resourcecorresponding to the transfer plane has been assigned to one of thecontrol planes or management planes, and the SNP state of the othercontrol planes is the busy state, i.e., the resource cannot be usedagain. The “assigned” state generally refers to that the resourcecorresponding to the SNP has been assigned, but the resource may also beassigned to a service with a higher priority or another specifiedservice.

To simplify the description, in following description of eachembodiment, the “available” and “potentially available” states areconsidered as an “available” state, and the “assigned” and “busy” statesare considered as an “occupied” state. Therefore, the inconsistency ofthe control plane resource state and the data plane resource state maybe divided into two cases, that is, “the control plane state isavailable, and the data plane state is occupied”, and “the control planestate is occupied, and the data plane state is available.”

In the overall flow of the above resource state monitoring method, whenthe network event state of the node meets the resource state detectiontriggering condition, the data plane resource state of the node and thecontrol plane resource state of the node are detected. Three embodimentsare taken as examples for the resource state detection triggeringcondition below, but the present invention is not limited thereto.

I. A Label Switching Path (LSP) Establishment Fails.

Referring to FIG. 2, a resource state monitoring method according to afirst embodiment of the present invention is shown. In this embodiment,a first node and a second node may be considered as the present node andan adjacent node thereof. The method includes.

Step 201: The first node initiates a connection establishing request tothe second node.

When the first node needs to communicate with the second node, the firstnode sends an LSP connection establishing request to the second node.

Step 202: A cross-connection of a data plane is created.

The first node and the second node respectively create the crossconnection of the data plane inside the node, so as to establish the LSPconnection.

Step 203: Whether the cross-connection of the data plane is createdsuccessfully or not is judged. Step 208 is carried out if thecross-connection of the data plane is created successfully, and step 204is carried out if the cross-connection of the data plane is not createdsuccessfully.

The creation of the cross-connection of the data plane in thisembodiment is a part of a process for establishing the LSP connection,so in general, the establishment of the LSP connection fails accordinglyif the creation of the cross-connection of the data plane fails.

Step 204: The data plane resource state of the node and the controlplane resource state of the node are detected.

In this embodiment, when the establishment of the LSP connection fails,the data plane resource states of the first node and the second node andthe control plane resource states of the first node and the second nodeshould be detected.

In this embodiment, the specific detecting process includes that thenode requires a Link Resource Manager (LRM) to detect the resourcestate, and the LRM, in cooperation with another control plane entity,e.g., a Termination and Adaptation Performer (TAP), checks a data planeresource, detects the cross state of the data plane and the connectionstate of the control plane, and compares to see whether the resourcecorresponding to the node is consistent in the control plane and thedata plane or not.

Step 205: Whether the data plane resource state of the node and thecontrol plane resource state of the node are consistent or not isjudged. Step 207 is carried out if the data plane resource state of thenode and the control plane resource state of the node are consistent,and step 206 is carried out if the data plane resource state of the nodeand the control plane resource state of the node are not consistent.

Step 206: The data plane resource state of the node and the controlplane resource state of the node are synchronized.

In this embodiment, if the data plane resource state of the node and thecontrol plane resource state of the node are not consistent, asubsequent processing may be carried out in three ways as follows.

1. Reporting to the Management Plane of the Node.

The inconsistency is reported to the management plane of the node, andthe management plane of the node makes a corresponding processing inaccordance with an actual situation, either by carrying out thesynchronization processing, or by restarting the network, or in anotherprocessing manner.

2. Employing an Automatic Mechanism.

When the states are detected to be inconsistent, the LRM directlycarries out a synchronization operation, and the specific action isdescribed below. When it is found that “the control plane state isavailable, and the data plane state is occupied”, a corresponding stateof the control plane may be automatically synchronized to be occupied.When it is found that “the control plane state is occupied, and the dataplane state is available”, the deletion of a connection using theresource is initiated on the control plane, thus synchronizing acorresponding state of the control plane to be available.

3. Triggering a Control Plane State Detection in a Horizontal Direction.

When the data plane and the control plane resource states of the nodeare detected to be inconsistent, the node may trigger detection so thatthe node and an adjacent node are consistent in the control planeresource state.

The synchronization is carried out by adjusting the control planeresource state to be consistent with the data plane resource state inthis embodiment, but it is understood that, the synchronization may alsobe carried out by adjusting the data plane resource state to beconsistent with the control plane resource state, and the specificprocess of which is similar to the above and will not be repeatedherein.

Step 207: The detection result of the data plane resource state of thenode and the control plane resource state of the node is reported to themanagement plane of the node.

In this embodiment, the detection result is reported to the managementplane of the node at all events.

Step 208: The network event state of the node continues to be monitored.

II. The Horizontal Resource State is not Consistent.

Referring to FIG. 3, a resource state monitoring method according to asecond embodiment of the present invention includes the following steps.

Step 301: A control plane resource state of an adjacent node isacquired.

In this embodiment, the control plane resource state of an adjacent nodein the ASON network topology is acquired, in which the adjacent may beeither adjacent in a physical position or adjacent in a logicalposition. The adjacent in a physical position refers to that two nodesare connected directly by a physical link without any other node betweenthe two nodes. The adjacent in a logical location refers to a forwardadjacency (FA) via multiple nodes between two nodes, or the two nodesare connected according to a layer network defined in G.805.

Step 302: Whether the control plane resource states of the two nodes areconsistent or not is judged. Step 307 is carried out if the controlplane resource states of the two nodes are consistent, and step 303 iscarried out if the control plane resource states of the two nodes arenot consistent.

In this embodiment, whether the states of each corresponding SNP on twoadjacent nodes in the control plane are consistent or not is judged toserve as a reference for judging whether the control plane resourcestates are consistent or not.

Step 303: The data plane resource state of the node and the controlplane resource state of the node are detected.

In this embodiment, when the control plane resource states of twoadjacent nodes are not consistent, the respective data plane resourcestate of each node and control plane resource state of each node shouldbe detected.

In this embodiment, the specific detecting process includes that thenode requires the LRM to detect the resource state, and the LRM, incooperation with another control plane entity (e.g., a TAP), checks adata plane resource, detects the cross state of the data plane and theconnection state of the control plane, and compares to see whether theresource corresponding to the node is consistent in the control planeand the data plane or not.

Step 304: Whether the data plane resource state of the node and thecontrol plane resource state of the node are consistent or not isjudged. Step 306 is carried out if the data plane resource state of thenode and the control plane resource state of the node are consistent,and step 305 is carried out if the data plane resource state of the nodeand the control plane resource state of the node are not consistent.

Step 305: The data plane resource state of the node and the controlplane resource state of the node are synchronized.

In this embodiment, if the data plane resource state of the node and thecontrol plane resource state of the node are not consistent, asubsequent processing may be carried out in two ways as follows.

1. Reporting to the Management Plane of the Node.

The inconsistency is reported to the management plane of the node, andthe management plane of the node makes a corresponding processing inaccordance with an actual situation, either by carrying out thesynchronization processing, or by restarting the network, or in anotherprocessing manner.

2. Employing an Automatic Mechanism.

When the states are detected to be inconsistent, the LRM directlycarries out a synchronization operation, and the specific action isdescribed below. When it is found that “the control plane state isavailable, and the data plane state is occupied”, a corresponding stateof the control plane may be automatically synchronized to be occupied.When it is found that “the control plane state is occupied, and the dataplane state is available”, the deletion of a connection using theresource is initiated on the control plane, thus synchronizing acorresponding state of the control plane to be available.

The synchronization is carried out by adjusting the control planeresource state to be consistent with the data plane resource state inthis embodiment, but it is understood that, the synchronization may alsobe carried out by adjusting the data plane resource state to beconsistent with the control plane resource state, and the specificprocess of which is similar to the above and will not be repeatedherein.

Step 306: The detection result of the data plane resource state of thenode and the control plane resource state of the node is reported to themanagement plane of the node.

In this embodiment, the detection result is reported to the managementplane of the node at all events.

Step 307: The network event state of the node continues to be monitored.

III. A Predetermined Time Threshold Value is Reached.

Referring to FIG. 4, a resource state monitoring method according to athird embodiment of the present invention includes.

Step 401: A detection time threshold value is set.

In this embodiment, a detection time threshold value is set when orbefore the ASON network runs, for instructing the LRM to detect theconsistency of the control plane resource state of each node and thedata plane resource state of each node when the network running timereaches the threshold value. It may be understood that, the detectionmay be performed in real time or every a period of time circularly.

Step 402: Whether the running time reaches the threshold value isjudged. Step 403 is carried out if the running time reaches thethreshold value, and step 407 is carried out if the running time doesnot reach the threshold value.

Step 403: The data plane resource state of the node and the controlplane resource state of the node are detected.

In this embodiment, when the predetermined detection time is reached,the data plane resource state of the node and the control plane resourcestate of the node should be detected.

In this embodiment, the specific detecting process includes that thenode requires the LRM to detect the resource state, and the LRM, incooperation with another control plane entity (e.g., a TAP), checks thedata plane resource, detects the cross state of the data plane and theconnection state of the control plane, and compares to see whether theresource corresponding to the node is consistent in the control planeand the data plane or not.

Step 404: Whether the data plane resource state of the node and thecontrol plane resource state of the node are consistent or not isjudged. Step 406 is carried out if the data plane resource state of thenode and the control plane resource state of the node are consistent,and step 405 is carried out if the data plane resource state of the nodeand the control plane resource state of the node are not consistent.

Step 405: The data plane resource state of the node and the controlplane resource state of the node are synchronized.

In this embodiment, if the data plane resource state of the node and thecontrol plane resource state of the node are not consistent, asubsequent processing may be carried out in three ways as follows.

1. Reporting to the Management Plane of the Node.

The inconsistency is reported to the management plane of the node, andthe management plane of the node makes a corresponding processing inaccordance with an actual situation, either by carrying out thesynchronization processing, or by restarting the network, or in anotherprocessing manner.

2. Employing an Automatic Mechanism.

When the states are detected to be inconsistent, the LRM directlycarries out a synchronization operation, and the specific action isdescribed below. When it is found that “the control plane state isavailable, and the data plane state is occupied”, a corresponding stateof the control plane may be automatically synchronized to be occupied.When it is found that “the control plane state is occupied, and the dataplane state is available”, the deletion of a connection using theresource is initiated on the control plane, thus synchronizing acorresponding state of the control plane to be available.

3. Triggering Control Plane State Detection in a Horizontal Direction.

When the data plane resource state of the node and the control planeresource state of the node are detected to be inconsistent, the node maytrigger consistency detection of the control plane resource state of theadjacent node.

The synchronization is carried out by adjusting the control planeresource state to be consistent with the data plane resource state inthis embodiment, but it is understood that, the synchronization may alsobe carried out by adjusting the data plane resource state to beconsistent with the control plane resource state, and the specificprocess of which is similar to the above and will not be repeatedherein.

Step 406: The detection result of the data plane resource state of thenode and the control plane resource state of the node is reported to themanagement plane of the node.

In this embodiment, the detection result is reported to the managementplane of the node at all events.

Step 407: The network event state of the node continues to be monitored.

The three conditions for triggering the consistency detection of thecontrol plane resource state of the node and the data plane resourcestate of the node described above may be selected or combined accordingto the actual situation, so as to increase the flexibility of theresource state monitoring method in the embodiments of the presentinvention.

A resource state monitoring device according to an embodiment of thepresent invention will be introduced below. Referring to FIG. 5, theresource state monitoring device according to an embodiment of thepresent invention includes an acquiring unit 501, a checking unit 502, atriggering unit 503, a detecting unit 504, and a reporting unit 505.

The acquiring unit 501 is adapted to acquire network event stateinformation of the node.

The checking unit 502 is adapted to judge whether the network eventstate information of the node meets a resource state detectiontriggering condition or not, and send a triggering notification if thenetwork event state information of the node meets the resource statedetection triggering condition.

The triggering unit 503 is adapted to trigger detection after receivingthe triggering notification of the checking unit 502.

The detecting unit 504 is adapted to detect the data plane resourcestate of the node and the control plane resource state of the node afterreceiving the triggering of the triggering unit 503.

The reporting unit 505 is adapted to report a detection result of thedetecting unit 504 to a management plane of the node.

In this embodiment, the checking unit 502 includes an establishmentmonitoring unit 5021 and/or a horizontal resource monitoring unit 5022and/or a time monitoring unit 5023.

The establishment monitoring unit 5021 is adapted to judge whether alabel switching path connection between the first node and the secondnode is established successfully or not, and send a notification to thetriggering unit 503 if a label switching path connection between thefirst node and the second node is established successfully.

The horizontal resource monitoring unit 5022 is adapted to judge whetherthe control plane resource states of two adjacent nodes in anautomatically switched optical network topology structure are consistentor not, and send a notification to the triggering unit 503 if thecontrol plane resource states of two adjacent nodes in the automaticallyswitched optical network topology structure are consistent.

The time monitoring unit 5023 is adapted to judge whether running timeof the automatically switched optical network reaches a detection timethreshold value or not, and send a notification to the triggering unit503 if the running time of the automatically switched optical networkreaches the detection time threshold value.

In this embodiment, one or more may be selected from the establishmentmonitoring unit 5021, the horizontal resource monitoring unit 5022 andthe time monitoring unit 5023 according to the actual situation.

A communication network according to an embodiment of the presentinvention is introduced below. Referring to FIG. 6, the communicationnetwork according to an embodiment of the present invention includesseveral nodes 601 (taking 3 nodes for example in this embodiment), acommunication control device 602 and a resource state monitoring device603.

The node 601 is adapted to communicate in the communication network.

The communication control device 602 is adapted to control each of thenodes 601 to communicate.

The resource state monitoring device 603 is adapted to acquire thenetwork event state information of each of the nodes 601, detect thedata plane resource state of each of the nodes 601 and the control planeresource state of each of the nodes 601 when the network event state ofeach of the nodes 601 is determined to meet the resource state detectiontriggering condition, and report the detection result to the managementplane of each of the nodes 601.

The resource state monitoring device includes an acquiring unit, achecking unit, a triggering unit, a detecting unit and a reporting unit.The functions and actions of the units are the same as those of theunits in FIG. 5, and the specific description may be obtained withreference to the above description, and will not be repeated herein.

Those with ordinary skill in the art may appreciate that, all or part ofthe steps in achieving the above embodiments of the method may beaccomplished by instructing related hardware by programs, and theprograms may be stored in a computer readable storage medium. Theprogram includes the following steps as executed:

In a running process of an automatically switched optical network,whether the network event state of the node meets the resource statedetection triggering condition or not is judged, and the data planeresource state of the node and the control plane resource state of thenode are detected if the network event state of the node meets theresource state detection triggering condition.

The aforementioned storage medium may be a read-only memory, a magneticdisk, an optical disc, and so on.

Though illustration and description of the present disclosure have beengiven with reference to preferred embodiments thereof, it should beappreciated by persons of ordinary skill in the art that various changesin forms and details can be made without deviation from the spirit andscope of this disclosure, which are defined by the appended claims.

1. A resource state monitoring method, wherein in a network runningprocess, the method comprises: acquiring network event state informationof a node; detecting a data plane resource state of the node and acontrol plane resource state of the node when the network event stateinformation of the node meets a resource state detection triggeringcondition; and reporting a detection result to a management plane of thenode.
 2. The resource state monitoring method according to claim 1,wherein the network event state information of the node meeting theresource state detection triggering condition comprises: judging whethera label switching path connection between the node and an adjacent nodeis established successfully or not; and determining that network eventstates of the node and the adjacent node meet the resource statedetection triggering condition if the label switching path connectionbetween the node and the adjacent node is not established successfully.3. The resource state monitoring method according to claim 2, before theprocess of judging whether a label switching path connection between thenode and an adjacent node is established successfully or not, the methodcomprising: initiating, by the node, a label switching path connectionestablishing request to the adjacent node; and returning, by theadjacent node, a label switching path connection establishing responseto the node after receiving the label switching path connectionestablishing request
 4. The resource state monitoring method accordingto claim 1, wherein the process of determining that network event statesof the node and the adjacent node meet the resource state detectiontriggering condition comprises: judging whether the control planeresource states of the node and the adjacent node in a network topologystructure are consistent or not, and determining that network eventstates of the node and the adjacent node both meet the resource statedetection triggering condition if the control plane resource states ofthe node and the adjacent node in the network topology structure are notconsistent.
 5. The resource state monitoring method according to claim1, wherein the determining that network event states of the node and theadjacent node meet the resource state detection triggering conditioncomprises: judging whether network running time reaches a predetermineddetection time threshold value or not, and determining that the node inthe network meets the resource state detection triggering condition ifthe network running time reaches the predetermined detection timethreshold value.
 6. The resource state monitoring method according toclaim 2, wherein the process of detecting a data plane resource stateand a control plane resource state of the node comprises: initiating, bythe node, a detecting request for the control plane resource state ofthe node and the data plane resource state of the node to a linkresource manager; and detecting, by the link resource manager, a crossstate of the data plane of the node and a connection state of thecontrol plane of the node.
 7. The resource state monitoring methodaccording to claim 4, wherein the process of detecting a data planeresource state and a control plane resource state of the node comprises:initiating, by the node, a detecting request for the control planeresource state of the node and the data plane resource state of the nodeto a link resource manager; and detecting, by the link resource manager,a cross state of the data plane of the node and a connection state ofthe control plane of the node.
 8. The resource state monitoring methodaccording to claim 5, wherein the process of detecting a data planeresource state and a control plane resource state of the node comprises:initiating, by the node, a detecting request for the control planeresource state of the node and the data plane resource state of the nodeto a link resource manager; and detecting, by the link resource manager,a cross state of the data plane of the node and a connection state ofthe control plane of the node.
 9. The resource state monitoring methodaccording to claim 2, further comprising: synchronizing the data planeresource state of the node and the control plane resource state of thenode if the detection result is that the data plane resource state ofthe node and the control plane resource state of the node are notconsistent.
 10. The resource state monitoring method according to claim4, further comprising: synchronizing the data plane resource state ofthe node and the control plane resource state of the node if thedetection result is that the data plane resource state of the node andthe control plane resource state of the node are not consistent.
 11. Theresource state monitoring method according to claim 5, furthercomprising: synchronizing the data plane resource state of the node andthe control plane resource state of the node if the detection result isthat the data plane resource state of the node and the control planeresource state of the node are not consistent.
 12. The resource statemonitoring method according to claim 9, wherein the process ofsynchronizing the data plane resource state of the node and the controlplane resource state of the node comprises: modifying the control planeresource state of the node into being occupied if the control planeresource state of the node is available and the data plane resourcestate of the node is occupied; and acquiring a control plane resource ofthe node corresponding to a data plane resource of the node, querying aconnection using the control plane resource of the node currently, anddeleting the connection so that the control plane resource state of thenode becomes available if the control plane resource state of the nodeis occupied and the data plane resource state of the node is available.13. The resource state monitoring method according to claim 1, furthercomprising: triggering consistency detection of the control planeresource states of the node and the adjacent node if the detectionresult is that the data plane resource state of the node and the controlplane resource state of the node are not consistent.
 14. A resourcestate monitoring device, comprising: an acquiring unit, adapted toacquire network event state information of a node; a checking unit,adapted to judge whether the network event state information of the nodemeets a resource state detection triggering condition or not, and send atriggering notification if the network event state information of thenode meets the resource state detection triggering condition; atriggering unit, adapted to trigger detection after receiving thetriggering notification of the checking unit; a detecting unit, adaptedto detect a data plane resource state of the node and a control planeresource state of the node after receiving the triggering detection ofthe triggering unit; and a reporting unit, adapted to report a detectionresult of the detecting unit to a management plane of the node.
 15. Theresource state monitoring device according to claim 14, wherein thechecking unit comprises at least one of: an establishment monitoringunit, adapted to judge whether a label switching path connection betweenthe node and an adjacent node is established successfully or not, andsend a notification to the triggering unit if the label switching pathconnection between the node and the adjacent node is not establishedsuccessfully; a horizontal resource monitoring unit, adapted to judgewhether the control plane resource states of the node and an adjacentnode in a network topology structure are consistent or not, and send anotification to the triggering unit if the control plane resource statesof the node and the adjacent node in the network topology structure arenot consistent; and a time monitoring unit, adapted to judge whethernetwork running time reaches a predetermined detection time thresholdvalue or not, and send a notification to the triggering unit if thenetwork running time reaches the predetermined detection time thresholdvalue.
 16. A communication network, comprising: several nodes, each ofwhich is adapted to communicate in a communication network; acommunication control device, adapted to control each of the nodes tocommunicate; and a resource state monitoring device, adapted to acquirenetwork event state information of each of the nodes, detect a dataplane resource state of each of the nodes and a control plane resourcestate of each of the nodes when the network event state information ofthe nodes meets a resource state detection triggering condition, andreport a detection result to a management plane of each of the nodes.17. The communication network according to claim 16, wherein theresource state monitoring device comprises: an acquiring unit, adaptedto acquire the network event state information of each of the nodes; achecking unit, adapted to judge whether the network event stateinformation of each of the nodes meets the resource state detectiontriggering condition or not, and send a triggering notification if thenetwork event state information of each of the nodes meets the resourcestate detection triggering condition; a triggering unit, adapted totrigger detection after receiving the triggering notification of thechecking unit; a detecting unit, adapted to detect the data planeresource state of each of the nodes and the control plane resource stateof each of the nodes after receiving the triggering detection of thetriggering unit; and a reporting unit, adapted to report the detectionresult of the detecting unit to the management plane of each of thenodes.
 18. A computer program product, stored on a computer readablemedium, having computer executable instructions for instructing one ormore digital processors to perform a resource state monitoring method,the computer readable medium comprising: instructions for acquiringnetwork event state information of a node; instructions for detecting adata plane resource state of the node and a control plane resource stateof the node when the network event state information of the node meets aresource state detection triggering condition; and instructions forreporting a detection result to a management plane of the node.